Your new package pull request met all of the guidelines for auto-merging and is scheduled to be merged when the mandatory waiting period (3 days) has elapsed.

Since you are registering a new package, please make sure that you have read the package naming guidelines: https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

Are you aware this is going to be made obsolete by JuliaLang/julia#46976? And JuliaLang/julia#45582 will alleviate the troubles in 1.9 (and will probably be also backported to 1.6 and 1.8)

Are you aware this is going to be made obsolete by JuliaLang/julia#46976? And JuliaLang/julia#45582 will alleviate the troubles in 1.9 (and will probably be also backported to 1.6 and 1.8)

I am aware of that PR. But I think it will not help on systems that come with an older version of libstdc++. Currently I work with a micromamba docker file that does not have the latest libstdc++ installed and I was forced to symlink a newer one that I installed via micromamba.

I understood that julia will check on startup whether the system's libstdc++ is newer, or did I misunderstand?

@giordano I was only aware of the first of the PRs. The second one does indeed make this package obsolete.
Maybe I don't register this package then but just leave as is ...

@giordano So please abort the merging of this package. Thanks for pointing me to your PRs.